-
-
Notifications
You must be signed in to change notification settings - Fork 33.1k
gh-137017: Fix Thread.is_alive()
to only return False after the underlying OS thread exits
#137315
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
gh-137017: Fix Thread.is_alive()
to only return False after the underlying OS thread exits
#137315
Conversation
…OS thread is fully cleaned up
@colesbury, gentle reminder on this PR when you have a moment. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @Abdoulrasheed. Looks good with a minor comment below
Thanks @Abdoulrasheed for the PR, and @colesbury for merging it 🌮🎉.. I'm working now to backport this PR to: 3.14. |
Thanks @Abdoulrasheed for the PR, and @colesbury for merging it 🌮🎉.. I'm working now to backport this PR to: 3.13. |
…the underlying OS thread exits (pythongh-137315) (cherry picked from commit aa9ceb1) Co-authored-by: Abdul <[email protected]>
…the underlying OS thread exits (pythongh-137315) (cherry picked from commit aa9ceb1) Co-authored-by: Abdul <[email protected]>
GH-138916 is a backport of this pull request to the 3.14 branch. |
GH-138917 is a backport of this pull request to the 3.13 branch. |
… the underlying OS thread exits (gh-137315) (gh-138917) (cherry picked from commit aa9ceb1) Co-authored-by: Abdul <[email protected]> Co-authored-by: Sam Gross <[email protected]>
|
… the underlying OS thread exits (gh-137315) (gh-138916) (cherry picked from commit aa9ceb1) Co-authored-by: Abdul <[email protected]> Co-authored-by: Sam Gross <[email protected]>
Ensure
Thread.is_alive()
only returns False after the underlying OS thread exits.Thread.is_alive
should only returnFalse
after a thread exits (once it's started) #137017